One year later it's still there. Is an expected behavior after all?
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: